feat: hide datasource legacy based on featureflag#11371
Conversation
Codecov Report
@@ Coverage Diff @@
## master #11371 +/- ##
==========================================
+ Coverage 66.12% 66.52% +0.39%
==========================================
Files 841 859 +18
Lines 40156 40965 +809
Branches 3685 3687 +2
==========================================
+ Hits 26554 27252 +698
- Misses 13501 13612 +111
Partials 101 101
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
|
@lilykuang would you mind giving this a look? |
nytai
left a comment
There was a problem hiding this comment.
LGTM, but I'm curious what's the motivation for this? Is the idea to fully deprecate the old datasource editor. We have been getting quite a few bug reports on the new datasource editor, are we certain the new datasource editor is at 100% feature parity?
|
LGTM once green |
|
retriggering CI, since #11433 merged |
SUMMARY
Hiding legacy datasource view based upon
react_crud_viewsflagBEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Flag: False
Flag: True
TEST PLAN
ENABLE_REACT_CRUD_VIEWSto falseUse Legacy Datasource Editorbtn is hidden inDatasourceModalviewADDITIONAL INFORMATION